Help topics | Getting Started | Advanced Info | FAQ

Introduction
The jv16 PowerTools contains a very advanced scripting engine which is totally independent from any Windows automation features and APIs and therefore it doesn't need any special DLLs or other components to work.

Basics
A script is a text file which can be edited with any text editor, such as Windows Notepad, but jv16 PowerTools also contains a very handy script editor. A script is basically a set instructions for jv16 PowerTools, it's a bit like Windows' .bat file but much more flexible and with a lot more features.

Advanced
The jv16 PowerTools script language supports
- If clauses (also internal if structures)
- If Else clauses
- For loops
- Variables

If you are familiar with any programming language, such as C/C++ or Java it will take about five minutes for you to learn the jv16 PowerTools script language.

The language's strength is it's built-in functions, you can see the complete script command reference from here.

Testing
A typical script file is just a list of script commands, therefore the easiest and the best way to test a script is to use the jv16 PowerTools' Console. It allows you to type script commands directly to the script engine. You can also use the console to create scripts, the Man and Syntax commands are a great help.

You can find a lot of example scripts from here or by typing "Examples" command (it's not actually a command but a script file) to the Console.

Usage
So what can you do with script files? Well, virtually anything. You can automate almost everything you will do with jv16 PowerTools, such as the removal of temp files or invalid registry entries. See the list of script commands to understand the power what a simple script file can contain.

Creating console commands
You can also create your own jv16 PowerTools console commands. Just create a script to the script directory, after that you can execute it from the console by writing it's name. You can also pass command line parameters from the console to your own script. This is done by variables called Par and NPar. The Par0, Par1, Par2 etc. variables contain the given command line parameters, the NPar0, NPar1, NPar2 etc. contain the numeric parameters.

For example, you have created a script called "test.jvb" to the script directory (usually \jv16 PowerTools\Scripts\). You can first of all run the script by simply writing "test" to the Console. But you can also pass command line parameters to it, so for example "test -hello" would also run the script like always but inside the script you could read the variable Par1 and it would contain the word "-hello". The Par0 will always contain the name of the actual command, in this case "test".
.:: Copyright 2000-2003 Macecraft Software